How's it going, do you need any help here?

Hey, working on Jest tests and manual testing too - should be here soonish

This one is ready for some reviews, thanks!

@thymikee @Esemesek
Any idea why those doctor e2e tests fails?

Azure fails with "EPERM: operation not permitted, mkdir 'D:'" when we try to create a temporary directory for testing, maybe something changed there? Sounds like Azure changing something, would be good to verify this in other PRs

I think this test fails randomly. We consider Windows failures as non-blocking since most of them are just flakiness in the Azure environment.

Do you feel like giving this one a go @thymikee @Esemesek before shipping? Since it's ready and failures are non-related, I'd love to have a final approval from your side.

Since this code is ready to go and this is our second attempt and rewriting this relatively major part of run-android, I am going to take it over and do the last round of testing myself.

I am hoping we can ship it next week, it should resolve some really annoying issues.

@thymikee: i have rebased the branch of this pr with the master into this branch https://github.com/tokyodrift1993/react-native-community-cli/tree/feature/buildApkFixes

@driiftkiing can you send a PR amending this one? :)

@driiftkiing can you send a PR amending this one? :)

just creating a new one? or something else?

Yup, a new one. Unless @krizzu is still interested in pursuing this, but let's assume he's not and make sure to attribute him for the work done when merging

@driiftkiing @thymikee
Been a while 🤖
I just rebased the code, tests are passing. I'm yet to test this, making sure that it works properly.

Ran some tests on custom android project, trying different configuration of build variants (with and without flavors) and it works.
Would love to have someone else do the sanity check as well 🙏

Thanks @krizzu, I am going to do another pass at it this week and ship it!

I will do also some tests, if i got the time

Thanks for the review @andriytsaryov. @grabbou I guess we can finally go ahead and merge it

Yes, that's on my todo list for tomorrow. When ready, I will create a new release.

I'd love to be able to run

npx react-native run-android --variant=developmentDebug --deviceId 931X1X9JW

and have it work. This PR seems to solve that. Anything holding this up getting merged in?

No, @pas256, this PR will be pulled in soon, once we merge a PR removing link and unlink.

if anyone is interested to use this PR until it is merged:

• created patch: https://gist.github.com/driiftkiing/09f3bd7bb125e6436a5caba7834f3a99
  • used for yarn v3
  • can be used like:

  diff --git a/package.json b/package.json
  --- a/package.json
  +++ b/package.json
     "resolutions": {
  +    "@react-native-community/cli-platform-android": "patch:@react-native-community/cli-platform-android@npm:6.3.0#.yarn/patches/@react-native-community-cli-platform-android-npm-6.3.0-1b9d17ef3a",
     },

• source: https://github.com/tokyodrift1993/react-native-community-cli/tree/krizzu/buildApkFixes--merged-v6.3.0
• merged v6.3.0
• (fixed lint & tests)
• should be compatible with react-native@0.67.2

command to run:

yarn react-native run-android --variant=developmentDebug

There hasn't been any activity on this pull request in the past 3 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days.

#1739 closes this one

🫡